Touchless payments at point-of-sale terminals

ABSTRACT

In some implementations, a method of providing contactless payments at a point of sale terminal includes: causing a point-of-sale terminal processing a transaction to display a machine-readable code, the machine-readable code encoding a web address; receiving a request from a device that scanned the machine-readable code, the request received at the web address; in response to receiving the request, causing the device that scanned the machine-readable code to output an interface that includes a prompt for input required to complete the transaction; receiving a response to the prompt; and sending an indication of the response to the prompt to the point-of-sale terminal to allow for completion of the transaction based on the response at the point-of-sale terminal through use of a physical token at the point-of-sale terminal.

TECHNICAL FIELD

The present application relates to value transfer cards and, moreparticularly, to systems and methods for allowing a customer to processa payment at a point-of-sale terminal without contacting thepoint-of-sale terminal.

BACKGROUND

Due to COVID-19, there is an increased desire among customers to avoidcontacting surfaces that numerous individuals may have already touched.Point of Sale (POS) terminals often require customer interaction inorder to complete a sale. For example, POS terminals often prompt forinput of a voluntary amount, such as a tipping amount. Often, eventhough a customer may have a payment card that allows for contactlesspayments, they may need to contact the POS terminal in order to completea purchase by, for example, inputting a tipping amount.

Further, point-of-sale terminals that require customer physicalinteraction may also be difficult to operate for some customers. Forexample, visually impaired users may have difficulty operatingpoint-of-sale terminals that may, for example, require input at atouchscreen display.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below, with reference to thefollowing drawings:

FIG. 1 is a schematic diagram illustrating an operating environment ofan example embodiment;

FIG. 2 is high-level schematic diagram of a computing device;

FIG. 3 shows a simplified organization of software components stored ina memory of the computing device of FIG. 2 ;

FIG. 4 shows an example point-of-sale terminal;

FIG. 5 shows a sequence diagram illustrating messages exchanged betweensystems illustrated in FIG. 1 ;

FIG. 6 illustrates, in flowchart form, an example method that may beperformed by a server;

FIG. 7 illustrates, in flowchart form, an example method that may beperformed by a point-of-sale terminal; and

FIG. 8 shows an example interface that may be displayed on a customerdevice.

Like reference numerals are used in the drawings to denote like elementsand features.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

In an aspect, a processor-implemented method is disclosed. The methodmay be performed by a server. The method may include: causing apoint-of-sale terminal processing a transaction to display amachine-readable code, the machine-readable code encoding a web address;receiving a request from a device that scanned the machine-readablecode, the request received at the web address; in response to receivingthe request, causing the device that scanned the machine-readable codeto output an interface that includes a prompt for input required tocomplete the transaction; receiving a response to the prompt; andsending an indication of the response to the prompt to the point-of-saleterminal to allow for completion of the transaction based on theresponse at the point-of-sale terminal through use of a physical tokenat the point-of-sale terminal.

Conveniently, in this way, a customer may have a true touchlessexperience at a point-of-sale terminal. That is, the customer maycomplete a transaction without ever having to contact the POS terminal.The customer may, instead, provide input responsive to any requisiteprompts on their own device, such as on a mobile device, but the POSterminal may still be used for processing the transaction after suchinput has been received. For example, a tipping amount may be input atthe customer's device and provided to the POS terminal so that acustomer may then tap a payment token, such as a near fieldcommunication (NFC) enabled value transfer card, at the POS terminal tocomplete the transaction.

In some implementations, the machine-readable code may encode a baseamount of a transaction. The request from the device may reference thebase amount of the transaction and the interface may indicate the baseamount of the transaction.

In some implementations, the machine-readable code may encode atransaction identifier. The request from the device may reference thetransaction identifier. The indication of the response to the prompt maybe sent to the point-of-sale terminal based on the transactionidentifier.

In some implementations, the machine-readable code may encode a hash anda digital signature. The request may include the hash and digitalsignature and the method may further include verifying the request basedon the hash and the digital signature.

In some implementations, the machine-readable code may further encoderandom data. The request may further include the random data and themethod may further include verifying that the request is not associatedwith a replay attack based on the random data.

In some implementations, the physical token may include one or more of:a payment card and a mobile device having a representation of a paymentcard stored thereon.

In some implementations, the prompt may be for input of an optionalamount to be added to a base amount to obtain a total amount prior tocompleting the transaction. The indication of the response to the promptmay indicate one or both of the optional amount or the total amount toallow the point-of-sale terminal to indicate that the transaction is tobe for the total amount prior to completing the transaction using thephysical token.

In some implementations, the method may include: receiving, from thepoint-of-sale terminal, an indication of a base amount of thetransaction; determining, based on the base amount of the transaction,that touchless payment is available, and wherein the machine-readablecode is caused to be displayed in response to determining that touchlesspayment is available.

In some implementations, the interface that includes the prompt maygenerate the prompt audibly to assist a visually-impaired operator ofthe device.

In some implementations, the method may further include receiving, fromthe point-of-sale terminal, a request for the indication of the responseto the prompt. The indication of the response to the prompt may be sentto the point-of-sale terminal in response to receiving the request forthe indication of the response to the prompt.

In yet another aspect, a server is disclosed. The server may include acommunications module. The server may include a processor coupled withthe communications module. The server may include a memory coupled tothe processor and storing processor-executable instructions which, whenexecuted by the processor, configure the server to perform a methoddescribed herein.

In another aspect, a computer-readable storage medium may be provided.The computer-readable storage medium may include processor-executableinstructions which, when executed, configure a processor to perform amethod described herein.

In yet another aspect, a method performed by a point-of-sale terminal isdisclosed. The method may include: obtaining a machine-readable code,the machine-readable code encoding a web address; displaying themachine-readable code; receiving, from a server associated with the webaddress, an indication of a response to a prompt; and displaying atransaction completion prompt based on the indication of the response,the transaction completion prompt prompting for completion of thetransaction through use of a physical token at the physical tokenreader.

In some implementations, the method may further include receiving inputof a base amount of the transaction through the input module. Themachine-readable code may encode the base amount of a transaction.

In some implementations, the machine-readable code may encode atransaction identifier.

In some implementations, the machine-readable code may encode a hash anda digital signature.

In some implementations, the machine-readable code may encode randomdata.

In some implementations, the physical token may include one or more of:a payment card and a mobile device having a representation of a paymentcard stored thereon.

In some implementations, the web address may be associated with aninterface that prompts for input of an optional amount to be added to abase amount to obtain a total amount prior to completing thetransaction. The indication of the response to the prompt may indicateone or both of the optional amount or the total amount. The method mayfurther include displaying the total amount prior to completing thetransaction using the physical token.

In some implementations, obtaining the machine-readable code mayinclude: sending the base amount to a server; and receiving themachine-readable code from the server.

In some implementations, the method may include determining, based onthe base amount of the transaction, that touchless payment is available.The machine-readable code may be displayed in response to determiningthat touchless payment is available.

In some implementations, the method may further include: receiving inputvia the input module, the input indicating readiness to complete thetransaction; and in response to receiving the input indicating readinessto complete the transaction, send a request for the indication of theresponse to the prompt to the server, and wherein the indication of theresponse to the prompt is received in response the request for theindication of the response to the prompt.

In yet another aspect, a point-of-sale terminal is described. Thepoint-of-sale terminal may include a physical token reader. Thepoint-of-sale terminal may include a communications module. Thepoint-of-sale terminal may include a display module. The point-of-saleterminal may include an input module. The point-of-sale terminal mayinclude a processor coupled with the communications module, the inputmodule, the display module and the physical token reader. Thepoint-of-sale terminal may include a memory coupled to the processor andstoring processor-executable instructions which, when executed by theprocessor, configure the point-of-sale terminal to perform a methoddescribed herein.

In another aspect, a computer-readable storage medium may be provided.The computer-readable storage medium may include processor-executableinstructions which, when executed, configure a processor to perform amethod described herein.

Other aspects and features of the present application will be understoodby those of ordinary skill in the art from a review of the followingdescription of examples in conjunction with the accompanying figures.

In the present application, the term “and/or” is intended to cover allpossible combinations and sub-combinations of the listed elements,including any one of the listed elements alone, any sub-combination, orall of the elements, and without necessarily excluding additionalelements.

In the present application, the phrase “at least one of . . . or . . . ”is intended to cover any one or more of the listed elements, includingany one of the listed elements alone, any sub-combination, or all of theelements, without necessarily excluding any additional elements, andwithout necessarily requiring all of the elements.

Example embodiments of the present application are not limited to anyparticular operating system, system architecture, mobile devicearchitecture, server architecture, or computer programming language.

Physical tokens can be used for making purchases at a point-of-saleterminal. Such physical tokens may be configured for tap-style paymentsin which the physical token is placed in a communication range of aphysical token reader to allow physical token data to be read from thephysical token. By way of example, physical tokens may include any oneor a combination of: payment cards (which may also be referred to asvalue transfer cards) and computing devices having a representation of apayment card stored thereon. By way of example, the physical token maybe a mobile device having a mobile wallet that stores a representationof a payment card.

A physical token may be connected to one or more accounts (such asbanking accounts) that store data and/or resources accessible to thecardholder. By way of example, the physical token may be associated witha bank account and/or a credit card account. The physical token may actas a credit card or a debit card.

The physical token may be configured for near-field communication (NFC)payment processing or for wireless communication-based paymentprocessing of another type. Notably, conventional POS terminals thatinteract with such physical tokens often do not provide a true touchlessexperience. For example, while a customer may use the physical token tosubmit payment through a tap of the physical token at the POS terminal,the customer may be required to contact the POS terminal in order toprovide other input. For example, a conventional POS terminal may promptthe customer for input of an optional payment amount, such as a tip, ormay prompt the customer for input of contact information such as anemail address to which a receipt may be delivered. Conveniently, one ormore POS terminals described herein may provide at least some customerswith a true touchless experience in which the customer is able toprocess the transaction, including responding to any requisite prompts,without contacting the POS terminal. As will be described below, in atleast some implementations, a customer may provide input responsive tosuch prompts on their own device and the responses may be sent to thePOS terminal so that the transaction may then be completed at the POSterminal.

FIG. 1 is a schematic operation diagram illustrating an operatingenvironment of an example embodiment.

As noted previously, in many conventional systems customers may berequired to provide input at a POS terminal 110 in order to complete atransaction. As illustrated, however, in FIG. 1 , in order to facilitatetrue touchless payments, the POS terminal 110 may communicate with atouchless transfer server 100. Such communication may be by way of thenetwork 130. The touchless transfer server 100 may also communicate witha customer device 150 and such communication may be by way of a network,such as the network 130.

The customer device 150 is a computing device that is associated with acustomer. By way of example, the customer device 150 may include any oneor more of: a mobile device, a tablet computer, a laptop computer, awearable computer, or a computing device of another type.

As will be described in greater detail below, the touchless transferserver 100 may interact with the customer device 150 to allow a customerto provide input at the customer device 150 so that at least some inputneed not be provided at the POS terminal 110 directly. Accordingly, thetouchless transfer server 100 may be or may be associated with a webserver.

The touchless transfer server 100 may also communicate the input to thePOS terminal 110 to allow the POS terminal 110 to process a transactionthat is based on the received input. Such communication may, forexample, be by way of a network, such as the network 130.

As illustrated, a point-of-sale (POS) terminal 110 may communicate witha transfer rail 120 which relays transaction data to an appropriateissuer system 124. Such communication may be via a network, such as thenetwork 130. The transfer rail 120 may also be referred to as a paymentrail.

The point-of-sale terminal is associated with an acquirer and thecommunication between the POS terminal 110 and the transfer rail 120 maybe by way of a back-end acquirer system. The POS terminal 110 may belocated at a location that is associated with a merchant. By way ofexample, the merchant may be a store, restaurant, gym, etc. The acquireris a merchant bank that accepts deposits associated with transactionsmade at the point-of-sale terminal and facilitates settlement anddeposit of those deposits into an account associated with the merchant.

While a single transfer rail 120 is illustrated in FIG. 1 , in practicethe POS terminal 110 may communicate with multiple transfer rails. Byway of example, the transfer rail 120 may include any one or acombination of Amex™, Visa™ and/or Mastercard™. Other transfer rails mayalso be used. The POS terminal and/or a back-end acquirer system incommunication with the POS terminal may, after obtaining data from aphysical token, such as a value transfer card or a mobile device havinga representation of a payment card which has engaged a physical tokenreader provided at the POS terminal, determine which of the transferrails is to be used. For example, the POS terminal/acquirer system maydetermine that the physical token is associated with Visa™ and may, inresponse, select the Visa™ payment rail or it may, instead, determinethat the physical token is associated with Mastercard™ and select theMastercard™ payment rail.

After a transfer rail is identified, the POS terminal/acquirer systemsends the transfer rail a message. The message may be sent through anetwork, such as the network 130. The message includes a value amountrepresenting an amount of value that is to be transferred to complete atransaction and physical token data such as a primary account number(PAN) associated with a physical token. The transfer rail identifies anassociated issuer based on the physical token data and communicates withthe identified issuer to process the transaction. More particularly, thetransfer rail 120 routes the message received from the POS terminal toan issuer system 124 for the identified issuer. The issuer system thendetermines whether the transaction is approved or denied based onpre-defined rules. The rules may, for example, consider any one or moreof: whether the cardholder has available funds, whether the merchant isof a type that is permitted, whether the transaction violates anyspending limits, etc.

When the issuer system determines whether to approve or deny thetransaction, it sends a message indicating the result of thisdetermination to the POS terminal 110 via the transfer rail 120. Theresult may then be displayed or otherwise output at the POS terminal110.

The issuer system 124, point-of-sale terminal 110, customer device 150,touchless transfer server 100, and the transfer rail 120 may be ingeographically disparate locations. Put differently, each of issuersystem 124, point-of-sale terminal 110, customer device 150, touchlesstransfer server 100, and the transfer rail 120 may be remote from othersof the issuer system 124, point-of-sale terminal 110, customer device150, touchless transfer server 100, and the transfer rail 120.

The issuer system 124, point-of-sale terminal 110, customer device 150,touchless transfer server 100, and the transfer rail 120 may each beboth a computer system and a computing device.

The network 130 is a computer network. In some embodiments, the network130 may be an internetwork such as may be formed of one or moreinterconnected computer networks. For example, the network 130 may be ormay include an Ethernet network, an asynchronous transfer mode (ATM)network, a wireless network, or the like. Additionally, oralternatively, the network 130 may be or may include one or more paymentnetworks. The network 130 may, in some embodiments, include a pluralityof distinct networks. For example, communications between certain of thecomputer systems may be over a private network whereas communicationsbetween other of the computer systems may be over a public network, suchas the Internet.

Referring now to FIG. 2 , a high-level operation diagram of an examplecomputing device 200 will now be described. The example computing device200 may be exemplary of the issuer system 124, point-of-sale terminal110, customer device 150, touchless transfer server 100, and/or transferrail 120.

The example computing device 200 includes numerous different modules.For example, as illustrated, the example computing device 200 mayinclude a processor 210, a memory 220, a communications module 230,and/or a storage module 240. As illustrated, the foregoing examplemodules of the example computing device 200 are in communication over abus 250.

The processor 210 is a hardware processor. The processor 210 may, forexample, be one or more ARM, Intel x86, PowerPC processors or the like.

The memory 220 allows data to be stored and retrieved. The memory 220may include, for example, random access memory, read-only memory, andpersistent storage. Persistent storage may be, for example, flashmemory, a solid-state drive or the like. Read-only memory and persistentstorage are a non-transitory computer-readable storage medium. Acomputer-readable medium may be organized using a file system such asmay be administered by an operating system governing overall operationof the example computing device 200.

The communications module 230 allows the example computing device 200 tocommunicate with other computing devices and/or various communicationsnetworks. For example, the communications module 230 may allow theexample computing device 200 to send or receive communications signals.Communications signals may be sent or received according to one or moreprotocols or according to one or more standards. For example, thecommunications module 230 may allow the example computing device 200 tocommunicate via a cellular data network, such as for example, accordingto one or more standards such as, for example, Global System for MobileCommunications (GSM), Code Division Multiple Access (CDMA), EvolutionData Optimized (EVDO), Long-term Evolution (LTE) or the like.Additionally, or alternatively, the communications module 230 may allowthe example computing device 200 to communicate using near-fieldcommunication (NFC), via WiFi™, using Bluetooth™, or via somecombination of one or more networks or protocols. In some embodiments,all or a portion of the communications module 230 may be integrated intoa component of the example computing device 200. For example, thecommunications module may be integrated into a communications chipset.

The storage module 240 allows the example computing device 200 to storeand retrieve data. In some embodiments, the storage module 240 may beformed as a part of the memory 220 and/or may be used to access all or aportion of the memory 220. Additionally, or alternatively, the storagemodule 240 may be used to store and retrieve data from persisted storageother than the persisted storage (if any) accessible via the memory 220.In some embodiments, the storage module 240 may be used to store andretrieve data in a database. A database may be stored in persistedstorage. Additionally, or alternatively, the storage module 240 mayaccess data stored remotely such as, for example, as may be accessedusing a local area network (LAN), wide area network (WAN), personal areanetwork (PAN), and/or a storage area network (SAN). In some embodiments,the storage module 240 may access data stored remotely using thecommunications module 230. In some embodiments, the storage module 240may be omitted and its function may be performed by the memory 220and/or by the processor 210 in concert with the communications module230 such as, for example, if data is stored remotely. The storage modulemay also be referred to as a data store.

Software comprising instructions is executed by the processor 210 from acomputer-readable medium. For example, software may be loaded intorandom-access memory from persistent storage of the memory 220.Additionally, or alternatively, instructions may be executed by theprocessor 210 directly from read-only memory of the memory 220.

The computing device 200 will include other components apart from thoseillustrated in FIG. 2 and the specific component set may differ based onwhether the computing device 200 is operating as the issuer system 124,point-of-sale terminal 110, customer device 150, touchless transferserver 100, and/or the transfer rail 120. For example, the computingdevice 200 may include one or more input modules, which may be incommunication with the processor 210 (e.g., over the bus 250). The inputmodules may take various forms including, for example, a mouse, amicrophone, a camera, a touchscreen overlay, a button, a sensor, etc. Byway of further example, the computing devices 200 may include one ormore output modules, which may be in communication with the processor210 (e.g., over the bus 250). The output modules include one or moredisplay modules which may be of various types including, for example,liquid crystal displays (LCD), light emitting diode displays (LED),cathode ray tube (CRT) displays, etc. By way of further example, theoutput modules may include a speaker.

Where the computing device 200 is operating as the POS terminal 110, thecomputing device 200 may include a physical token reader. The physicaltoken reader is configured for reading a physical token such as a valuetransfer card or a mobile device having a representation of a valuetransfer card stored thereon. The physical token reader may be orinclude a card slot which facilitates communication with the physicaltoken through physical contact and/or a contactless reader such as anear field communication (NFC) reader which may facilitate communicationwith the physical token through communication protocols that do not relyon physical contact with the physical token.

As noted above, the computing device 200 may include one or more inputmodules and/or one or more output modules. For example, where thecomputing device 200 is operating as the POS terminal 110 it may includeone or more input modules such as a touchscreen display and/or a keypadthat may be configured to receive user input. Even where the POSterminal 110 is configured for providing true touchless payments inwhich a customer does not need to touch the POS terminal 110, the inputmodules may be used by an operator, for example. Where the computingdevice 200 is operating as the POS terminal 110, it may also include adisplay module which is used for displaying a user interface thatfacilitates payment processing.

When the computing device 200 is operating as the customer device 150,the input modules may include a camera or scanner than may be used toscan a machine-readable code as will be explained more fully in thediscussion of FIGS. 5 to 7 below.

FIG. 3 depicts a simplified organization of software components storedin the memory 220 of the example computing device 200 (FIG. 2 ). Asillustrated, these software components include an operating system 300and an application software 310.

The operating system 300 is software. The operating system 300 allowsthe application software 310 to access the processor 210 (FIG. 2 ), thememory 220, and the communications module 230 of the example computingdevice 200 (FIG. 2 ). The operating system 300 may be, for example,Google™ Android™, Apple™ iOS™, UNIX™, Linux™, Microsoft™ Windows™, AppleOSX™ or the like.

The application software 310 adapts the example computing device 200, incombination with the operating system 300, to operate as a deviceperforming a particular function. For example, the application software310 may cooperate with the operating system 300 to adapt a suitableembodiment of the example computing device 200 to operate as the issuersystem 124, point-of-sale terminal 110, customer device 150, touchlesstransfer server 100, and/or the transfer rail 120.

While a single application software 310 is illustrated in FIG. 3 , inoperation the memory 220 may include more than one application software310 and different application software 310 may perform differentoperations.

Referring now to FIG. 4 , an example POS terminal 110 is illustrated.The POS terminal includes a physical token reader which, in the example,includes a wireless physical token reader configured for near fieldcommunications. The physical token reader may be used by tapping aphysical token at a particular region 404 of the POS terminal 110. Theparticular region 404 is a sensing region. That is, when the physicaltoken is placed at or near the particular region, the POS terminal 110is able to communicate with the physical token to obtain physical tokendata.

The POS terminal 110 includes one or more output modules. In theexample, the output modules include a display module 402. The displaymodule 402 may, in at least some implementations, be a touchscreendisplay. In such cases, the display module 402 is both an output moduleand an input module.

The POS terminal 110 may include an input module of another type insteadof or in addition to a touchscreen display. By way of example, thedisplayed POS terminal 110 includes a keypad 406. The input module maybe used by an operator in order to setup a transaction. By way ofexample, the operator may input a base amount of a transaction. In someinstances, the POS terminal may include or be associated with a scannersuch as a bar-code reader which may be used to scan bar-codes that aredisplayed on tags associated with merchandise. In such instances, theoperator may not input the base amount of the transaction directly; thebase amount may be determined by a computer having access to price data.

By way of further example, in some instances, the POS terminal 110 maybe associated with a computer system which allows an operator to inputorder information that may be used to calculate a base amount that isprovided directly to the POS terminal 110. For example, the computersystem may be a merchant terminal that may allow an operator to selectitems for an order from a predefined list, such as a list associatedwith a menu, and the merchant terminal may then calculate a base amountfor a transaction and send it to the POS terminal.

The POS terminal 110 may, in some instances, include other physicaltoken readers apart from the wireless physical token reader. Forexample, a card slot may be included and may be arranged so that when avalue transfer card is inserted in the card slot, one or more pins orpads associated with the card may align with pads or pins provided inthe POS terminal 110 that are intended for reading data from the card.

By way of further example, in some instances, the physical token readersmay include a magnetic reader which is configured for reading data froma magnetic strip associated with a value transfer card.

Reference is now made to FIG. 5 . FIG. 5 illustrates a sequence diagram500, similar to a Unified Modelling Language (UML) sequence diagram,that shows how the customer device 150, touchless transfer server 100,POS terminal 110, transfer rail 120 and the issuer system 124 maycommunicate in some embodiments, and, in particular, depicting messagesexchanged therebetween in processing a transaction. That is, suchmessages may be used for initiating a data transfer or initiating atransfer of value.

The operations that are performed by the customer device 150, touchlesstransfer server 100, POS terminal 110, transfer rail 120 and the issuersystem 124 in exchanging the messages illustrated in the sequencediagram and/or in performing various operations referred to herein, maybe performed by processors executing processor-executable instructionsstored in a memory. The processors may be coupled to a communicationsmodule which may be used in sending and/or receiving the variousmessages.

In the following description of the sequence diagram 500, discussion ismade of various messages being sent and received via a computer networksuch as, for example, network 130. In some embodiments, the exchangedmessages may be implemented as messages. However, in other embodiments,some or all of the illustrated messages may not correspond to messagesper se when sent over the computer network but may instead beimplemented using techniques such as for example remote procedure call(RPC) and/or web services application programming interfaces (APIs). Forexample, it may be that various message pairs illustrated in FIG. 5correspond to an RPC or a web service API call and a reply or callbackin response to that call.

As illustrated, at the beginning of sequence, at 502, the POS terminal110 may receive transaction setup data, such as a base amount of atransaction. The base amount may be received through an input modulethat is configured for receiving operator input. The input module may beprovided on the POS terminal or on an associated system that iscommunicably coupled with the POS terminal 110. By way of example, insome implementations, the base amount may be received via direct inputon a keypad 406 (FIG. 4 ) provided at the POS terminal. In otherinstances, another point of sale system may receive input that may beused to determine the base amount (e.g., by scanning a bar code or byselecting an item for purchase from a list of available items) and thebase amount may then be sent to the POS terminal 110. A base amount of atransaction may be an amount of a transaction that a customer isrequired to pay and the base amount of the transaction may exclude anoptional amount (also known as a voluntary amount and/or a variableamount), such as an amount for a tip.

In some implementations, the POS terminal 110 may only allow a customerto use their customer device 150 as part of the transaction if touchlesspayments are likely to be available. For example, in some instances, acustomer may only be permitted to use tap-style payments fortransactions that are under a certain threshold. In at least some suchimplementations, the POS terminal 110 may determine at 504, based on thebase amount of the transaction, whether touchless payment is available.

By way of example, in some instances, tap-style or other touchlesspayments may only be permitted for transactions that are under athreshold amount. The POS terminal 110 may, therefore, compare the baseamount, or an amount that is based on the base amount, to a thresholdsuch as $200. If the amount exceeds the threshold (i.e., if touchlesspayment is not available), then 506 to 530 may not be performed and thetransaction may instead be completed in a traditional manner since thecustomer may be required to contact the POS terminal anyway in order toinput a credential, such as a personal identification number (PIN). Putdifferently, if the POS terminal 110 determines that the customer isrequired or is likely to be required to contact the POS terminal 110 aspart of an authentication procedure, then the operations that allow acustomer device 150 to be used in place of the POS terminal may not beperformed.

As noted above, in assessing whether the customer is likely to berequired to contact the POS terminal 110 for authentication purposes,the POS terminal may consider the base amount of the transaction. Thebase amount may, prior to the comparison, include or be adjusted toinclude other non-optional amounts, such as a tax amount. The baseamount may, prior to the comparison, also be adjusted to include anexpected optional amount. For example, the expected optional amount maybe determined based on a typical rate, such as a typical tipping rate.The typical tipping rate may be, for example, 15%, 18%, 20%, or anotheroptional amount. The typical rate may be determined automatically insome implementations; for example, based on past transactions at thesame merchant or same POS terminal 110 or in the same geographic region(e.g., the same country). The adjustment to the base amount to accountfor such amounts is to reduce the likelihood that a transaction thatinitially was less than a threshold for which contact with the POSterminal for authentication purposes is not required will exceed thethreshold after user input of an optional amount, such as a tip, isreceived. Put differently, this is to attempt to avoid a scenario inwhich a customer device 150 is used to receive input of a tip or anotheroptional amount and then the customer is required to contact the POSterminal 110 for authentication purposes.

In some implementations, 504 may not be performed as a precondition to506 and onward. Rather, the POS terminal 110 may allow customers to usea customer device 150 during the transaction even when the customer willbe required to contact the POS terminal for authentication purposes. Insuch implementations, the use of the customer device 150 may reduceinteractions with the POS terminal 110 by the customer even ifinteractions are not entirely eliminated.

The POS terminal 110 may then obtain and display a machine-readablecode. In at least some implementations, the POS terminal 110 may do soin response to determining that touchless payment is available (at 504).

In some implementations, the POS terminal 110 may obtain themachine-readable code from the touchless transfer server 100. Forexample, the POS terminal 110 may send a message 506 to the touchlesstransfer server 100. The message 506 may be referred to as a coderequest message. The message 506 may include an indication of the baseamount of transaction. The message 506 may include one or moreidentifier such as a point-of-sale terminal identifier and/or a merchantidentifier. The message 506 may also include random data, such as arandom number which may be produced by a random number generator.

The touchless transfer server 100 receives the message 506 whichincludes the base amount of the transaction. In response to receivingthe message 506, the touchless transfer server 100 generates amachine-readable code based on the contents of the message 506.

The machine-readable code may, in some implementations, be a quickresponse (QR) code. The machine-readable code may encode various data.For example, the machine-readable code may encode the base amount of thetransaction. The machine-readable code may encode a transactionidentifier. The machine-readable code may encode a point-of-saleterminal identifier and/or a merchant identifier. The machine-readablecode may include random data such as the random data provided in themessage 506.

The machine-readable code may encode a link such as, for example, a webaddress. The web address is an address associated with a web server thatis provided by or is associated with the touchless transfer server 100.The web address may be a uniform resource locator (URL). The web addressmay be associated with an interface. That is, the web address may be anaddress for a web server that serves the interface to a device that hasscanned the machine-readable code.

The machine-readable code may encode security or verification data. Forexample, the machine-readable code may encode a hash. The touchlesstransfer server 100 may generate the hash based on other data encoded inthe machine-readable code. For example, the hash may be generated basedon any one or a combination of: the link/web address, the base amount ofthe transaction, the point-of-sale terminal identifier and/or a merchantidentifier, the transaction identifier and/or the random data.

The machine-readable code may be digitally signed by the touchlesstransfer server 100 and/or may encode a digital signature.

In some implementations, at least some of the data that is encoded inthe machine-readable code may be encoded as parameters associated withthe web address that is encoded in the machine-readable code. Forexample, any one or a combination of: the hash, the base amount of thetransaction, the point-of-sale terminal identifier, the merchantidentifier, the transaction identifier, the random data and/or thedigital signature may be encoded as parameters, such as URL parameters,for the URL. Conveniently, in this way, when a customer scans themachine-readable code with a customer device 150, the customer device150 may be directed to the web address associated with the touchlesstransfer server 100 and may pass the web address such data asparameters.

The touchless transfer server 100 may, after preparing themachine-readable code, send a message 508 to the POS terminal 110. Themessage 508 includes the machine-readable code. In sending themachine-readable code to the POS terminal 110, the touchless transferserver 100 causes the machine-readable code to be displayed at the POSterminal 110. The POS terminal 110 receives the message 508 and, indoing so, receives the machine-readable code. The POS terminal 110 may,at 510, display the machine-readable code at a display module 402 (FIG.4 ) associated with the POS terminal 110.

The operator of the POS terminal 110 may then ask a customer to scan orread the machine-readable code using a customer device 150. A customermay point a camera or other scanner associated with the customer device150 at the displayed machine-readable code while a reader application isenabled on the customer device 150. The customer device 150 at 512obtains a representation of the machine-readable code. That is, thereader application may decode the machine-readable code in order toobtain data contained therein. In doing so, the reader application mayidentify the web address included in the machine-readable code. Thereader application may then provide a selectable option to activate theweb address or it may automatically activate the web address.

The customer device 150 which scanned the machine-readable code, maythen send a message 514 to the touchless transfer server 100. Themessage may be a request to retrieve content and, more particularly, arequest to retrieve an interface. The request may be in the form of anHTTP GET in some implementations. The request may be sent by a webbrowser associated with the customer device 150 in at least someimplementations. For example, the reader application may pass a URL andany associated URL parameters decoded from the machine-readable code tothe web browser which then uses the URL, complete with any parameters,to retrieve the interface.

The touchless transfer server 100 receives the message 514. That is, thetouchless transfer server 100 receives a request from the customerdevice 150 for the interface and receives any data that may be passed tothe touchless transfer server 100 as, for example, URL parameters.Accordingly, the request received at the touchless transfer server 100may reference any one or a combination of: the base amount of thetransaction, the transaction identifier, the hash, the digitalsignature, the random data, the point-of-sale identifier, and/or themerchant identifier.

In some implementations, in response to receiving the message 514, thetouchless transfer server 100 may, at 522, verify the message 514. Thatis, the touchless transfer server 100 may verify the request. Suchverification may be based on the hash, the digital signature and/or therandom data. The verification may, for example, ensure that the requestis not associated with a replay attack, that the data has not beentampered with and/or that the request was generated based on anauthorized machine-readable code. The verification that the request wasgenerated based on an authorized machine-readable code may be based onthe digital signature. That is, the touchless transfer server 100 mayverify that the signature is a valid signature. The verification thatthe request was not associated with a replay attack may rely on therandom data. The hash may be used to verify that the data has not beentampered with.

After the touchless transfer server 100 verifies the request and, inresponse to receiving the request, the touchless transfer server maycause the device that scanned the machine-readable code to output aninterface that includes a prompt for input required to complete thetransaction. More specifically, the touchless transfer server 100 sendsa message 518 to the customer device 150. The message may include theinterface.

The interface may be a web page and may be displayed in a web browser onthe customer device 150. An example interface 800 is illustrated in FIG.8 . The interface may include a base amount indicator 802 indicating thebase amount of the transaction and/or a merchant indicator 804indicating a merchant associated with the transaction as indicated bythe merchant identifier.

The interface may be a generic interface that is the same for allmerchants or a plurality of merchants or it may be a merchant-specificinterface that is applicable for a particular merchant. For example,while not illustrated in FIG. 8 , the interface 800 may include a logofor the merchant. By way of example, the interface 800 may be retrievedby the touchless transfer server 100 from a data store or memory basedon the merchant identifier.

The interface may include a prompt 806. The prompt may, as illustratedin FIG. 8 , be a prompt for input of an optional amount to be added tothe base amount to obtain a total amount prior to completing thetransaction.

In some implementations, the interface, which may include the prompt,may generate the prompt audibly to assist a visually-impaired operatorof the customer device 150. That is, the interface may be output at aspeaker associated with the customer device 150.

Referring again to FIG. 5 , the customer device 150 receives the message518 and displays the interface at 520. The customer device 150 thenreceives, at 522, input via the interface. The input may be a responseto the prompt 806. The customer device 150 then sends a message 524 tothe touchless transfer server 100. The message 524 includes the responseto the prompt.

The touchless transfer server 100 may then send an indication of theresponse to the prompt to the point-of-sale terminal to allow forcompletion of the transaction based on the response at the point-of salethrough use of a physical token at the POS terminal 110. In someimplementations, the touchless transfer server 100 may push theindication of the response to the prompt to the appropriatepoint-of-sale terminal (e.g., using an identifier such as thepoint-of-sale identifier or transaction identifier to identify theappropriate POS terminal). In other implementations, the indication ofthe response to the prompt may be provided using a pull technique. Forexample, the POS terminal may send a message 528 to the touchlesstransfer server 100. The message 528 is a request for an indication ofthe response to the prompt. The request may be sent periodically (e.g.,the POS terminal 110 may repeatedly attempt to retrieve the indicationof the response to the prompt from the touchless transfer server 100until it becomes available) or it may be sent in response to inputreceived (at 526) at an input module of the POS terminal. The inputindicates readiness to complete the transaction. For example, it may bethat the operator of the POS terminal, who is an employee of themerchant, provides an input at the POS terminal after their customer hasindicated that they have finished providing a response to the promptthrough the interface 800 provided on the customer device 150. Then,when the POS terminal 110 receives such input, it may send the message524 requesting the indication of the response to the prompt.

The touchless transfer server 100 then sends the indication of theresponse to the prompt in a message 530. The indication of the responseto the prompt may indicate one or both of the optional amount or thetotal amount (i.e., the amount that includes both the base amount andthe optional amount) to allow the point-of-sale terminal to indicatethat the transaction is to be for the total amount prior to completingthe transaction using the physical token.

In some instances, the indication of the response to the prompt may besent to the POS terminal based on an identifier such as the POSidentifier and/or the transaction identifier. One or both suchidentifiers may be included in the message 528 and used by the touchlesstransfer server 100 to identify the appropriate response to the promptto be used to provide the message 530.

The POS terminal 110 receives the message 530 (and thus, the indicationof the response to the prompt) and displays, at 532, a transactioncompletion prompt based on the indication of the response. Thetransaction completion prompt prompts for completion of the transactionthrough use of a physical token at the physical token reader. Thetransaction completion prompt may display the total amount of thetransaction (i.e., the amount that includes the base amount and anyoptional amount). By way of example, the transaction completion promptmay be: “The total amount of your transaction is $149.70. Tap your cardto pay.”

The transaction completion prompt may prompt for use of a physical tokento complete the transaction. The prompt may prompt the customer toinsert a payment card at a physical token reader, to swipe payment cardhaving a magnetic strip and/or to tap a physical token. A physical tokenmay include one or more of: a payment card and a mobile device having arepresentation of a payment card stored thereon.

A customer may then manipulate their physical token in accordance withthe prompt to allow the POS terminal 110 to read the physical token. ThePOS terminal obtains physical token data from the physical token at 534.Physical token data may include, for example, a PAN, an expiry date,verification data (e.g., a CVV number) and/or a token holder. The tokenholder may identify an entity that the token was issued to and/or isassociated with.

The POS terminal 110 then sends a transaction processing request to anappropriate transfer rail 120 in a message 536. The POS terminal 110 mayidentify the appropriate transfer rail based on the physical token dataand may send the message 536 to the identified transfer rail 120. Thetransaction processing request may include or be based on the physicaltoken data. The transaction processing request includes an amount of thetransaction, which may be the total amount that includes both the baseamount and the optional amount obtained through input at the customerdevice.

The transfer rail 120 then identifies an issuer system 124 to relay themessage to based on the physical token data in the message 536. Thetransfer rail 120 then relays the message to the identified issuersystem 124 as a message 538.

The issuer system 124 performs a real-time adjudication procedure basedon the message 538 in order to instantly determine whether thetransaction is to be approved or declined. Then, the issuer system 124sends an indication of whether the transaction was approved or declinedin a message 540 through the transfer rail 120. The transfer rail 120then relays this message to the POS terminal 110 as a message 542. ThePOS terminal then, at 544, displays a transaction result indicator,indicating whether the transaction was approved or declined.

Each of the systems illustrated in FIG. 5 may be considered to performan associated method. By way of example, the issuer system 124 performsa method that includes the operations described as being performed bythe issuer system 124 or a portion thereof, the transfer rail 120performs a method that includes the operations described as beingperformed by the transfer rail 120 or a portion thereof, the POSterminal 110 performs a method that includes the operations described asbeing performed by the POS terminal 110 or a portion thereof, thetouchless transfer server 100 performs a method that includes theoperations described as being performed by the touchless transfer server100 or a portion thereof, and the customer device 150 performs a methodthat includes the operations described as being performed by thecustomer device 150 or a portion thereof. A memory associated with eachof these systems may include computer-executable instructions which,when executed, configure the associated system to perform the associatedmethod, or a portion thereof.

By way of example, reference is now made to FIG. 6 , which shows, inflowchart form, an example method 600 that may be performed by atouchless transfer server 100. The method 600 may be for obtaining aresponse to prompts required by a POS terminal using a customer device150.

Operations starting with operation 602 and continuing onward areperformed by the processor 210 (FIG. 2 ) of a computing device 200executing software comprising instructions such as may be stored in thememory 220 of the computing device 200. For example, the operations ofthe method 600 may be performed by the touchless transfer server 100.More particularly, processor-executable instructions may, when executed,configure a processor 210 of the touchless transfer server 100 toperform the method 600. In some embodiments, the operations of method600 may be performed by the touchless transfer server 100 in conjunctionwith one or more other computing systems, such as the POS terminal 110and/or a customer device 150.

The operations 602 and onward may be the same or similar to thosedescribed above with reference to the sequence diagram 500 of FIG. 5 andthe discussion of the operations 602 and onward will be made byreference to the operations in the sequence diagram 500.

At an operation 602, the touchless transfer server 100 may cause apoint-of-sale terminal processing a transaction to display amachine-readable code. The machine-readable code may encode a webaddress. Operation 602 may be performed in the manner described abovewith reference to 502 to 510 of the sequence diagram.

Next, at operation 604, the touchless transfer server 100 may receive arequest from a device that scanned the machine-readable code. Therequest may be received at the web address. Operation 604 may beperformed as described above with reference to 514 of the sequencediagram 500 of FIG. 5 .

Next, at an operation 606, the touchless transfer server 100 may verifythe request. Operation 606 may be performed as described above withreference to 516 of the sequence diagram 500 of FIG. 5 .

Next, at an operation 608, the touchless transfer server 100 may causethe customer device 150 to output an interface that includes a promptfor input required to complete the transaction. Operation 608 may beperformed as described above with reference to 518 of the sequencediagram 500 of FIG. 5 .

Next, at an operation 610, the touchless transfer server 100 may receivea response to the prompt. Operation 610 may be performed as describedabove with reference to 524 of the sequence diagram 500 of FIG. 5 .

Next, at an operation 612, the touchless transfer server 100 may receivea request for an indication of the response to the prompt from the POSterminal. Operation 612 may be performed as described above withreference to 528 of the sequence diagram 500 of FIG. 5 .

Next, at an operation 614, the touchless transfer server 100 may send anindication of the response to the prompt to the POS terminal. Operation614 may be performed as described above with reference to 530 of thesequence diagram 500 of FIG. 5 .

Reference is now made to FIG. 7 , which shows, in flowchart form, anexample method 700 that may be performed by a POS terminal 110. Themethod 700 may be for obtaining a response to prompts required by thePOS terminal using a customer device 150.

Operations starting with operation 702 and continuing onward areperformed by the processor 210 (FIG. 2 ) of a computing device 200executing software comprising instructions such as may be stored in thememory 220 of the computing device 200. For example, the operations ofthe method 700 may be performed by the POS terminal 110. Moreparticularly, processor-executable instructions may, when executed,configure a processor 210 of the POS terminal 110 to perform the method700. In some embodiments, the operations of method 700 may be performedby the POS terminal 110 in conjunction with one or more other computingsystems, such as the touchless transfer server 100.

The operations 702 and onward may be the same or similar to thosedescribed above with reference to the sequence diagram 500 of FIG. 5 andthe discussion of the operations 702 and onward will be made byreference to the operations in the sequence diagram 500.

At an operation 702, the POS terminal 110 receives input of a baseamount of a transaction. Operation 702 may be performed in the mannerdescribed above with reference to 502 of the sequence diagram.

Next, at an operation 704, the POS terminal 110 determines, from thebase amount, that touchless payment is available. Operation 704 may beperformed in the manner described above with reference to 504 of thesequence diagram.

Next, at an operation 706, the POS terminal 110 obtains amachine-readable code. Operation 706 may be performed in the mannerdescribed above with reference to 506 to 508 of the sequence diagram.

Next, at an operation 708, the POS terminal 110 displays themachine-readable code. Operation 708 may be performed in the mannerdescribed above with reference to 510 of the sequence diagram.

Next, at an operation 710, the POS terminal 110 receives inputindicating readiness to complete the transaction. Operation 710 may beperformed in the manner described above with reference to 526 of thesequence diagram.

In response to receiving the input indicating readiness to complete thetransaction, the POS terminal 110 may, at operation 712, send a requestfor an indication of the response to the prompt to the touchlesstransfer server. Operation 712 may be performed in the manner describedabove with reference to 528 of the sequence diagram.

Then, at an operation 714, the POS terminal 110 receives an indicationof the response to the prompt from the touchless transfer server.Operation 714 may be performed in the manner described above withreference to 530 of the sequence diagram.

At an operation 716, the POS terminal 110 then displays a transactioncompletion prompt. Operation 716 may be performed in the mannerdescribed above with reference to 532 of the sequence diagram.

At an operation 718, the POS terminal 110 obtains physical token datafrom a physical token. Operation 718 may be performed in the mannerdescribed above with reference to 534 of the sequence diagram.

Then, at operation 720, the POS terminal 110 completes the transactionbased on the physical token data. Operation 720 may be performed in themanner described above with reference to 536 to 544 of the sequencediagram.

Conveniently, at least some methods and systems described herein maywork with numerous types of customer equipment since the customer device150 need only have the ability to scan a machine-readable code and a webbrowser to cooperate with other components described herein.

Further conveniently, at least some methods and systems described hereinmay be deployed through a software update to existing POS terminalswithout having to obtain all new POS terminals.

Further conveniently, at least some method and systems described hereinmay be the same irrespective of payment method. For example, a customercould pay using any payment card and the experience remains the same.That is, the customer could use their customer device 150 to input theresponses to the prompts and may afterwards determine whether they wishto use credit card or debit card. The experience is the sameirrespective of which card they select.

Further conveniently, at least some methods and system described hereinmay allow customers to store, on their own customer device, preferencesfor a particular merchant that may be used to auto-populate responses toprompts for a transaction with that particular merchant. For example, acookie could be stored on the customer device which may be used to trackcustomer preferences. The cookie may be stored on the customer's devicesuch that the next time they visit the contactless payment URL, thecookie may be retrieved and used to identify preferences. For example, atip amount may be automatically populated with a last tip amount.

At least some methods and systems described herein may also be used, forexample, to aid visually impaired users. As noted above, such customersmay be presented with voice prompts instead of visual prompts on theircustomer device.

It will be understood that the applications, modules, routines,processes, threads, or other software components implementing thedescribed method/process may be realized using standard computerprogramming techniques and languages. The present application is notlimited to particular processors, computer languages, computerprogramming conventions, data structures, or other such implementationdetails. Those skilled in the art will recognize that the describedprocesses may be implemented as a part of computer-executable codestored in volatile or non-volatile memory, as part of anapplication-specific integrated chip (ASIC), etc.

As noted, certain adaptations and modifications of the describedembodiments can be made. Therefore, the above discussed embodiments areconsidered to be illustrative and not restrictive.

The invention claimed is:
 1. A server comprising: a communicationsmodule; a processor coupled with the communications module; and a memorycoupled to the processor and storing processor-executable instructionswhich, when executed by the processor, configure the server to: receive,from a point-of-sale terminal processing a transaction, an indication ofa base amount of the transaction; determine, based on the base amount ofthe transaction, that touchless payment is available; in response todetermining that touchless payment is available, cause the point-of-saleterminal to display a machine-readable code, the machine-readable codeencoding a web address; receive a request from a device that scanned themachine-readable code, the request received at the web address; inresponse to receiving the request, cause the device that scanned themachine-readable code to output an interface that includes a prompt forinput required to complete the transaction wherein the prompt is forinput of an optional amount to be added to a base amount to obtain atotal amount prior to completing the transaction; receive a response tothe prompt; and send an indication of the response to the prompt to thepoint-of-sale terminal to allow for completion of the transaction basedon the response at the point-of-sale terminal through use of a physicaltoken at the point-of-sale terminal.
 2. The server of claim 1, whereinthe machine-readable code encodes a base amount of a transaction andwherein the request from the device references the base amount of thetransaction and the interface indicates the base amount of thetransaction.
 3. The server of claim 1, wherein the machine-readable codeencodes a transaction identifier and wherein the request from the devicereferences the transaction identifier, and wherein the indication of theresponse to the prompt is sent to the point-of-sale terminal based onthe transaction identifier.
 4. The server of claim 1, wherein themachine-readable code further encodes a hash and a digital signature andwherein the request further includes the hash and the digital signatureand wherein the instructions further cause the server to verify therequest based on the hash and the digital signature.
 5. The server ofclaim 4, wherein the machine-readable code further encodes random dataand wherein the request further includes the random data and wherein theinstructions further cause the server to verify that the request is notassociated with a replay attack based on the random data.
 6. The serverof claim 1, wherein the physical token includes one or more of: apayment card and a mobile device having a representation of a paymentcard stored thereon.
 7. The server of claim 1, wherein the indication ofthe response to the prompt indicates one or both of the optional amountor the total amount to allow the point-of-sale terminal to indicate thatthe transaction is to be for the total amount prior to completing thetransaction using the physical token.
 8. The server of claim 1, whereinthe interface that includes the prompt generates the prompt audibly toassist a visually-impaired operator of the device.
 9. The server ofclaim 1, wherein the instructions further configure the server to:receive, from the point-of-sale terminal, a request for the indicationof the response to the prompt and wherein the server sends theindication of the response to the prompt to the point-of-sale terminalin response to receiving the request for the indication of the responseto the prompt.
 10. A method comprising: receiving, from a point-of-saleterminal processing a transaction, an indication of a base amount of thetransaction; determining, based on the base amount of the transaction,that touchless payment is available; in response to determining thattouchless payment is available, causing the point-of-sale terminal todisplay a machine-readable code, the machine-readable code encoding aweb address; receiving a request from a device that scanned themachine-readable code, the request received at the web address; inresponse to receiving the request, causing the device that scanned themachine-readable code to output an interface that includes a prompt forinput required to complete the transaction, wherein the prompt is forinput of an optional amount to be added to a base amount to obtain atotal amount prior to completing the transaction; receiving a responseto the prompt; and sending an indication of the response to the promptto the point-of-sale terminal to allow for completion of the transactionbased on the response at the point-of-sale terminal through use of aphysical token at the point-of-sale terminal.
 11. The method of claim10, wherein the machine-readable code encodes a base amount of atransaction and wherein the request from the device references the baseamount of the transaction and the interface indicates the base amount ofthe transaction.
 12. The method of claim 10, wherein themachine-readable code encodes a transaction identifier and wherein therequest from the device references the transaction identifier, andwherein the indication of the response to the prompt is sent to thepoint-of-sale terminal based on the transaction identifier.
 13. Themethod of claim 10, wherein the machine-readable code further encodes ahash and a digital signature and wherein the request further includesthe hash and the digital signature and wherein the method furtherincludes verifying the request based on the hash and the digitalsignature.
 14. The method of claim 13, wherein the machine-readable codefurther encodes random data and wherein the request further includes therandom data and wherein the method further includes verifying that therequest is not associated with a replay attack based on the random data.15. The method of claim 10, wherein the physical token includes one ormore of: a payment card and a mobile device having a representation of apayment card stored thereon.
 16. The method of claim 10, and wherein theindication of the response to the prompt indicates one or both of theoptional amount or the total amount to allow the point-of-sale terminalto indicate that the transaction is to be for the total amount prior tocompleting the transaction using the physical token.
 17. The method ofclaim 10, wherein the interface that includes the prompt generates theprompt audibly to assist a visually-impaired operator of the device. 18.The method of claim 10, further comprising: receiving, from thepoint-of-sale terminal, a request for the indication of the response tothe prompt and wherein the indication of the response to the prompt issent to the point-of-sale terminal in response to receiving the requestfor the indication of the response to the prompt.